4.1 add routing context to hello message #701
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Include the routing context configured in the connection URI in the Hello message. This enables the server to make routing decisions with the same information provided to the driver.
For example with the URI
neo4j://localhost:7687?policy=fast®ion=eu
the driver will send the map:{'policy': 'fast', 'region': 'eu'}
in the Hello message's metadata with the keyrouting
.Since
bolt
is for direct connections the map is configured with{'routing': null}
inform that the sever should not route queries.